Repository navigation
chore(deps-dev): bump storybook from 10.2.13 to 10.6.2 - #3458
Conversation
Bumps [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) from 10.2.13 to 10.6.2. - [Release notes](https://github.com/storybookjs/storybook/releases) - [Changelog](https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md) - [Commits](https://github.com/storybookjs/storybook/commits/v10.6.2/code/core) --- updated-dependencies: - dependency-name: storybook dependency-version: 10.6.2 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
|
PR author is in the excluded authors list. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
🟢 Tier 1 — TrivialDocs, images, lock files, a dependency bump, or an automated release. No functional code changes detected. Why this tier:
Review process: Auto-merge once CI passes. No human review required. Stats
|
Duplicate code analysisNo new duplicate code introduced by this PR. jscpd compared this branch against |
| "rimraf": "^4.4.1", | ||
| "serve": "^14.0.0", | ||
| "storybook": "^10.2.10", | ||
| "storybook": "^10.6.2", |
There was a problem hiding this comment.
🔵 minor — Storybook core moves to 10.6.2, but the @storybook/* framework, addons and eslint plugin stay on 10.1.4
storybook is bumped to ^10.6.2, but @storybook/nextjs, @storybook/addon-docs, @storybook/addon-links, @storybook/addon-themes (all ^10.1.4) and eslint-plugin-storybook (pinned 10.1.4) are unchanged. yarn.lock still resolves them, along with @storybook/react, @storybook/preset-react-webpack and @storybook/core-webpack, to 10.1.4. These packages import storybook/internal/* and are released in lockstep with core. Storybook's own version check and storybook doctor flag mismatches like this, and the mix can break storybook dev and storybook build. Their storybook: ^10.1.4 peer range accepts 10.6.2, so yarn won't warn. Fix: bump every @storybook/* 10.x package and eslint-plugin-storybook to 10.6.2 in this PR, for example with npx storybook@10.6.2 upgrade.
Advisory. Fix if it is a small defect in code this PR changes; otherwise reply in the thread. Do not widen the PR or touch files it did not already change. How to respond
PR Review
1 finding(s): 🔴 0 critical · 🟠 0 major · 🔵 1 minor 1 posted as inline comment(s) on the changed lines. Severity is the reviewer's own estimate and is used for ordering, not filtering. No finding blocks merge automatically; a maintainer decides. |
Deep Review✅ No critical issues found. This is a dev-only dependency bump — 🔵 P3 nitpicks (1)
Reviewers (8): correctness, testing, maintainability, project-standards, security, previous-comments, agent-native, learnings-researcher. Testing gaps:
No finding blocks merge automatically. A maintainer will expect P0/P1 findings in code this PR changes to be fixed; P2/P3 are your call -- fix or reply. Never fix findings about surrounding code here; reply instead. Do not widen the PR. How to respond |
E2E Test Results✅ All tests passed • 455 passed • 1 skipped • 1475s
Tests ran across 4 shards in parallel. |
wrn14897
left a comment
There was a problem hiding this comment.
Minor/patch dependency bump, CI green.
| "rimraf": "^4.4.1", | ||
| "serve": "^14.0.0", | ||
| "storybook": "^10.2.10", | ||
| "storybook": "^10.6.2", |
There was a problem hiding this comment.
🔵 minor — Storybook core bumped to 10.6.2 while framework, addons and eslint plugin stay on 10.1.4
Bump @storybook/nextjs, @storybook/addon-docs, @storybook/addon-links, @storybook/addon-themes (lines 111-115) and eslint-plugin-storybook (line 138) to 10.6.2 in the same PR (e.g. npx storybook@10.6.2 upgrade), then regenerate yarn.lock. Today yarn.lock resolves storybook@10.6.2 next to @storybook/nextjs, @storybook/react, @storybook/builder-webpack5, @storybook/preset-react-webpack, @storybook/csf-plugin and @storybook/react-dom-shim at 10.1.4 (yarn.lock ~10781-11040). Storybook expects every @storybook/* package to run the same version as core. The 10.1.4 framework and builder import storybook/internal/* from 10.6.2, which only works if those internals did not change across five minor releases. The ^10.1.4 peer ranges let yarn accept this mix without complaint, and storybook doctor flags it as a version mismatch.
Advisory. Fix if it is a small defect in code this PR changes; otherwise reply in the thread. Do not widen the PR or touch files it did not already change. How to respond
Bumps storybook from 10.2.13 to 10.6.2.
Release notes
Sourced from storybook's releases.
... (truncated)
Changelog
Sourced from storybook's changelog.
... (truncated)
Commits
5f00d7dBump version from "10.6.1" to "10.6.2" [skip ci]b3ac816Core: Cover component file name escaping in generated story imports243c06bMerge pull request #36726 from storybookjs/sidnioulz/patch-internal-v11d0c7fa2Merge pull request #36526 from storybookjs/validate/preact-11b49ded6Merge pull request #36525 from storybookjs/fix/angular-vite-analog-2-7-3e067572Merge pull request #35664 from storybookjs/bill/fix-leaky-types01331a5Merge pull request #36419 from storybookjs/kasper/sb-2060-yarn1-proxy-remote-...a17b725Bump version from "10.6.0" to "10.6.1" [skip ci]3077af4Merge pull request #36310 from storybookjs/fix/init-vitest-range-stderr22bf9dfMerge pull request #36214 from storybookjs/ghengeveld/restore-change-detectio...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.